System and method to auto create aircraft maintenance records by aircraft data

ABSTRACT

A processor-implemented method for automatically creating aircraft maintenance records and work logs during aircraft maintenance operations is disclosed. The method comprises retrieving, using a processor, fault data, testing data, maintenance data, and status data regarding line replaceable units (LRUs) on an aircraft via a central maintenance computer (CMC) on the aircraft; automatically collecting from a remote terminal on the aircraft data regarding maintenance operations performed using the remote terminal; automatically recording, by the processor, in a maintenance database the fault data, testing data, maintenance data, status data, and data regarding maintenance operations performed using the remote terminal; and automatically populating, by the processor using data in the maintenance database, information in a plurality of fields in a maintenance work log.

TECHNICAL FIELD

The technology described in this patent document relates generally toaircraft maintenance systems and more particularly to aircraftmaintenance systems for automatically recording maintenance actions andcreating aircraft maintenance records.

BACKGROUND

Documenting aircraft maintenance activities is necessary even though thetime available for maintenance personnel to document their maintenanceactivities may be limited. Often documenting is done later when themaintenance personnel are back in their office, and are typicallyperformed manually. This may lead to important information not beingincluded in maintenance records.

Hence, it is desirable to provide systems and methods for automaticallyrecording maintenance actions. Furthermore, other desirable features andcharacteristics of the present disclosure will become apparent from thesubsequent detailed description and the appended claims, taken inconjunction with the accompanying drawings and the foregoing technicalfield and background.

SUMMARY

This summary is provided to describe select concepts in a simplifiedform that are further described in the Detailed Description. Thissummary is not intended to identify key or essential features of theclaimed subject matter, nor is it intended to be used as an aid indetermining the scope of the claimed subject matter.

A processor-implemented method for automatically creating aircraftmaintenance records and work logs during aircraft maintenance operationsis disclosed. The method includes retrieving, using a processor, faultdata, testing data, maintenance data, and status data regarding linereplaceable units (LRUs) on an aircraft via a central maintenancecomputer (CMC) on the aircraft; automatically collecting from a remoteterminal on the aircraft data regarding maintenance operations performedusing the remote terminal; automatically recording, by the processor ina maintenance database, the fault data, testing data, maintenance data,status data, and data regarding maintenance operations performed usingthe remote terminal; and automatically populating, by the processorusing data in the maintenance database, information in a plurality offields in a maintenance work log.

A maintenance record creation module configured to automatically createaircraft maintenance records and work logs during aircraft maintenanceoperations is disclosed. The maintenance record creation module includesone or more processors on an aircraft configured by programminginstructions on non-transient computer readable media. The maintenancerecord creation module is configured to retrieve fault data, testingdata, maintenance data, and status data regarding line replaceable units(LRUs) on an aircraft via a central maintenance computer (CMC) on theaircraft; automatically collect, from a remote terminal on the aircraft,data regarding maintenance operations performed using the remoteterminal; automatically record, in a maintenance database, the faultdata, testing data, maintenance data, status data, and data regardingmaintenance operations performed using the remote terminal; andautomatically populate, using data in the maintenance database,information in a plurality of fields in a maintenance work log.

An aircraft equipped with a maintenance system configured toautomatically create aircraft maintenance records and work logs duringaircraft maintenance operations is disclosed. The aircraft includes aplurality of line replaceable units (LRUs), a central maintenancecomputer (CMC) configured to communicate with the LRUs via an avionicssystem communication bus, and a remote terminal on the aircraft. Theremote terminal is configured to: retrieve fault data, testing data,maintenance data, and status data regarding the LRUs via the CMC;automatically collect data regarding maintenance operations performedusing the remote terminal; automatically record in a maintenancedatabase the fault data, testing data, maintenance data, status data,and data regarding maintenance operations performed using the remoteterminal; automatically populate, using data in the maintenancedatabase, information in a plurality of fields in a maintenance worklog; automatically generate a report identifying data recorded in themaintenance database during the performance of maintenance operations;automatically update, using data in the maintenance database, fields ina listing of life limited parts; and automatically alert a maintainer tocomplete certain pre-determined fields not automatically populated bythe processor but mandated for completion by governing authority.

BRIEF DESCRIPTION OF THE DRAWINGS

Aspects of the present disclosure are best understood from the followingdetailed description when read with the accompanying figures, whereinlike numerals denote like elements, and

FIG. 1 is a block diagram depicting example avionics systems on anexample aircraft, in accordance with some embodiments;

FIG. 2 is a block diagram depicting an example maintenance system, inaccordance with some embodiments;

FIG. 3 is a process flow chart depicting an example process in anaircraft maintenance system for automatically creating aircraftmaintenance records and work logs during aircraft maintenanceoperations, in accordance with some embodiments; and

FIG. 4 is a process flow chart depicting an example process in anaircraft maintenance system for automatically recommending maintenancesteps to maintenance personnel, in accordance with some embodiments.

DETAILED DESCRIPTION

The subject matter described herein discloses apparatus, systems,techniques and articles for automatically creating aircraft maintenancerecords and work logs during aircraft maintenance operations.Additionally, subject matter described herein discloses apparatus,systems, techniques and articles for recommending steps to be performedwhen troubleshooting faults during maintenance operations. The followingdetailed description is merely exemplary in nature and is not intendedto limit the invention or the application and uses of the invention. Asused herein, the word “exemplary” means “serving as an example,instance, or illustration.” Thus, any embodiment described herein as“exemplary” is not necessarily to be construed as preferred oradvantageous over other embodiments. All embodiments described hereinare exemplary embodiments provided to enable persons skilled in the artto make or use the invention and not to limit the scope of the inventionwhich is defined by the claims. Furthermore, there is no intention to bebound by any expressed or implied theory presented in the precedingtechnical field, background, summary, or the following detaileddescription.

FIG. 1 is a block diagram depicting example avionics systems on anexample aircraft 100 and a maintenance system 102 that is configured toautomatically record avionics system fault information, automaticallydetect and record maintenance actions taken, and automatically fillfields in maintenance records 101 such as work logs. The exampleaircraft includes a plurality of line replaceable units (LRUs) 104 thatcan communicate status information to a central maintenance computer(CMC) 106 via a communication bus 108, such as an avionics systemcommunication bus (ASCB). The example aircraft also includes a remoteterminal 110 and a data store 112, both of which are part of the examplemaintenance system 102. The example maintenance system 102 furtherincludes a recommender system 114 that is situated remotely from theaircraft.

The LRUs 104 in the example aircraft 100 may include various aircraftcomponents such as an IGV actuator, a fuel module, a surge controlvalve, a bleed valve, a lube module, a starter/generator system, anexciter, and others. The example CMC 106 is configured to retrieve, viathe ASCB 108, status information regarding the LRUs 104, such as theLRU's software/hardware part number, LRU's serial number, time and dateof LRU replacement, time and date of LRU reset, and other statusinformation.

The example remote terminal 110 may be implemented using any suitablehardware platform and is realized as a computer-implemented orcomputer-based device having the hardware, software, firmware, and/orprocessing logic needed to carry out the various techniques andmethodologies described herein. The example remote terminal 110 can beused by maintenance personnel when performing maintenance actions onavionics systems (e.g., LRUs) and is configured to automatically captureLRU status information from the CMC 106, automatically record the LRUstatus information in the data store 112, and automatically capture andrecord in the data store 112 maintenance actions performed using theremote terminal 110.

The example remote terminal 110 is also configured to automatically fillentries in maintenance records commonly used in the industry such aswork logs 101. The example remote terminal is configured toautomatically fill pre-existing fields (e.g., industry standard fields)in the work logs 101 and automatically record on the work logs 101detailed descriptions of troubleshooting steps performed by maintenancepersonnel.

The example remote terminal 110 is further configured to cooperate withthe recommender system 114 in providing suggestions to maintenancepersonnel regarding maintenance steps to perform. The examplerecommender system 114 is configured for use by maintenance personnel totroubleshoot avionics faults and includes a ground-based terminal thatmay be implemented using any suitable hardware platform. In this regard,the ground-based terminal can be realized in any common form factorincluding, but not limited to: a desktop computer; a mobile computer(e.g., a tablet computer, a laptop computer, or a netbook computer); asmartphone; a video game device; a digital media player; a piece of homeentertainment equipment; a digital camera or video camera; a wearablecomputing device (e.g., smart watch, smart glasses, smart clothing); orthe like. Each ground-based terminal supported by the recommender system114 is realized as a computer-implemented or computer-based devicehaving the hardware, software, firmware, and/or processing logic neededto carry out the various techniques and methodologies described herein.

The example recommender system 114 is configured to assist themaintenance personnel in troubleshooting the avionics faults by makingsuggestions based on the stored LRU status information and storedinformation regarding maintenance actions performed that are stored inthe data store 112. The example recommender system 114 may incorporatevarious machine learning techniques and algorithms to form maintenanceaction suggestions for the maintenance personnel.

FIG. 2 is a block diagram depicting an example maintenance system 200.The example maintenance system 200 includes a maintenance recordcreation module 202 in a remote terminal 203 onboard an aircraft and arecommender system 204. The example maintenance record creation module202 includes a plurality of modules configured to capture and storeinformation regarding various avionics systems in a maintenance database206 and a plurality of modules configured to retrieve information fromthe maintenance database 206 for automatically filling fields in variousdocuments and reports. The example maintenance record creation module202 configured to automatically create aircraft maintenance records andwork logs during aircraft maintenance operations.

The example maintenance record creation module 202 may be implementedusing a controller in an aircraft remote terminal. The controllerincludes at least one processor and a computer-readable storage deviceor media encoded with programming instructions for configuring thecontroller. The processor may be any custom-made or commerciallyavailable processor, a central processing unit (CPU), a graphicsprocessing unit (GPU), an application specific integrated circuit(ASIC), a field programmable gate array (FPGA), an auxiliary processoramong several processors associated with the controller, asemiconductor-based microprocessor (in the form of a microchip or chipset), any combination thereof, or generally any device for executinginstructions.

The computer readable storage device or media may include volatile andnonvolatile storage in read-only memory (ROM), random-access memory(RAM), and keep-alive memory (KAM), for example. KAM is a persistent ornon-volatile memory that may be used to store various operatingvariables while the processor is powered down. The computer-readablestorage device or media may be implemented using any of a number ofknown memory devices such as PROMs (programmable read-only memory),EPROMs (electrically PROM), EEPROMs (electrically erasable PROM), flashmemory, or any other electric, magnetic, optical, or combination memorydevices capable of storing data, some of which represent executableprogramming instructions, used by the controller.

The example maintenance record creation module 202 is configured tofacilitate comprehensive recording of maintenance actions performedusing the remote terminal 203. In an example operating scenario, when amaintainer (e.g., maintenance personnel) commences maintenanceoperations the maintainer switches the aircraft to maintenance modethrough a cockpit switch. The example maintenance record creation module202 is configured to record every action performed by the maintainerthrough the remote terminal 203 as the maintainer traverses throughdifferent pages in the remote terminal while troubleshooting avionicsfaults. An example flow of operations followed by a maintainer using theremote terminal 203 includes the following: (a) the maintainer accessesactive fault pages (for active fault messages); (b) the maintainer viewsdetails of the fault(s); (c) the maintainer views member (e.g., LRU)system status for member experiencing the fault; and (d) the maintainerinitiates the Built-in-test/System test for the member experiencing thefault. The example maintenance record creation module 202 is configuredto capture and record the messages received and the actions taken by themaintainer. After maintenance is completed, the example maintenancerecord creation module 202 can automatically generate a report detailingthe aircraft data recorded regarding the maintenance operationsperformed on the avionics units.

The example maintenance record creation module 202 is also configured tocapture maintenance actions performed by examining aircraft data via anaircraft bus. Example maintenance actions that may be captured includethe following: (1) the replacement of an LRU, which may be identified byexamining CMC retrieved configuration data; (2) the identification of amodule reset, which may be identified by monitoring aircraft data for acircuit breaker switch status or monitoring the AC/DC bus statusparameters since a power cycle is associated with a module reset; (3)the identification of a CMC test performed and the results from the CMCtest, which can be retrieved directly from the CMC because the CMC canmaintain the history of CMC tests performed and the test results in CMCpersistent storage; (4) the identification of and results received froma performed electrical check (e.g., a short test), which may beretrieved from avionics systems; and (5) the identification of andresults received from a performed status test, which may be retrievedfrom avionics systems.

The example maintenance record creation module 202 is also configured toautomatically fill certain fields in maintenance records. As an example,FAA Form 337 is used to record major repairs and major alterations madeto an aircraft avionics or a component part thereof. The person whoperforms or supervises a major repair or major alteration is required toprepare FAA Form 337. The example maintenance record creation module 202is configured to automatically fill certain fields in FAA Form 337. Theexample maintenance record creation module 202 is also configured toautomatically fill certain fields in other maintenance records such aswork logs. The example fields that may be auto filled include: partnumber, serial number, description, and time in service. The examplemaintenance record creation module 202 is configured to record partnumber and serial number information retrieved from the CMC on themaintenance records and configured to auto fill the description fieldwith actions performed at the remote terminal by the maintainer andcaptured by the module. The example maintenance record creation module202 is further configured to retrieve the time in service informationfor an LRU from the CMC, which tracks the time in service for each LRU.

The example maintenance record creation module 202 is also configured toupdate fields in a life limited parts list. Many operators/ownersmaintain a separate record of life limited parts that identifies thename of the part, part number, serial number, date of installation,total time in-service, date removed, signature and certification numberof the person who performed trouble-shooting. The example maintenancerecord creation module 202 is configured to automatically update thelife limited parts list using data from work logs.

The example maintenance record creation module 202 is additionallyconfigured to generate user alerts for alerting a user to manually fillin certain mandatory fields (e.g., FAA mandated fields) required forcompleting a work log. The example maintenance record creation module202 can then provide a report which can function as the formal work logrelated to avionics faults troubleshooting.

The example maintenance record creation module 202 includes an aircraftdata retrieval module 208, a remote terminal maintenance action trackermodule 210, and a recorder module 212. The aircraft data retrievalmodule 208 is configured to retrieve, via the CMC 214, fault dataregarding LRUs on the aircraft, LRU replacement data, LRU reset data,CMC test data, electrical check data, and LRU status data. The remoteterminal maintenance action tracker module 210 is configured to trackand collect data regarding maintenance actions performed by a maintainerusing the remote terminal 203. The recorder module 212 is configured torecord in the maintenance database 206, the data retrieved by theaircraft data retrieval module 208 and the data collected by the remoteterminal maintenance action tracker module 210.

The example maintenance record creation module 202 further includes areport generator module 216, a work log field populating module 218, amaintenance report field populating module 220, and maintainer alertingmodule 222. The report generator module 216 is configured toautomatically generate an aircraft data report 217 of the aircraft datacollected and recorded in the maintenance database during maintenanceoperations. The work log field populating module 218 is configured toautomatically populate, using the data in the maintenance database,information in a plurality of fields in a maintenance work log 219. Themaintenance report field populating module 220 is configured toautomatically update, using the data in the maintenance database, fieldsin a maintenance report 221 such as a listing of life limited parts. Themaintainer alerting module 222 is configured to automatically alert amaintainer via a user interface 223 to complete certain pre-determinedfields not automatically populated by the maintenance record creationmodule 202 but mandated for completion by governing authority.

The recommender system 204 may be implemented using a controller in anaircraft remote terminal, is configured for use by maintenance personnelto troubleshoot avionics faults, and includes a ground-based terminalthat may be implemented using any suitable hardware platform. Theexample recommender system 204 is configured to assist the maintenancepersonnel in troubleshooting the avionics faults by making suggestionsbased on the stored LRU status information and stored informationregarding maintenance actions performed that are stored in themaintenance database 206. The example recommender system 204 mayincorporate various machine learning techniques and/or algorithms toform maintenance action suggestions for the maintenance personnel. Acomplete avionics maintenance profile for an aircraft may also beprepared using maintenance data collected over time. Further,maintenance personnel may receive insights regarding the way to resolvea fault, which may not be visible from viewing maintenance manuals.Since the example maintenance record creation module 202 is configuredto record every action performed by a maintainer while troubleshootingavionics system, the example recommender system can access recordedsteps and alert a maintainer to steps that may be missing frommaintenance manuals.

FIG. 3 is a process flow chart depicting an example process 300 in anaircraft maintenance system for automatically creating aircraftmaintenance records and work logs during aircraft maintenanceoperations. The order of operation within the process is not limited tothe sequential execution as illustrated in FIG. 3, but may be performedin one or more varying orders as applicable and in accordance with thepresent disclosure.

The example process 300 includes retrieving, via a processor on theaircraft, fault data, testing data, maintenance data, and status dataregarding LRUs on the aircraft via a CMC on the aircraft (operation302). The fault data may include fault information retrieved by the CMCregarding the LRU over the ASCB. The testing data may include theidentity of any diagnostic tests performed regarding the LRU and theresults from the performed diagnostic tests. The identity of diagnostictests performed may include the identity of ASCB parametersinvestigated. The testing data may also include the identity ofperformed electrical checks and the results therefrom. The electricalchecks may include tests for shorts performed by monitoring Smart andnon-Smart LRU configurations. The maintenance data may include dataidentifying aircraft avionics system configuration changes made duringthe maintenance operations (e.g., whether an LRU was replaced during themaintenance operations), data identifying whether an LRU was resetduring maintenance operations, and the identity of maintenance manualsreferred to for troubleshooting. The status data may include dataindicating the operational status of the LRU and configurationinformation regarding the LRU wherein the configuration information mayinclude the software and hardware configuration of the LRU and itsassociated non-smart LRUs.

The example process 300 also includes automatically collecting, from aremote terminal on the aircraft, maintenance data regarding maintenanceoperations performed by maintenance personnel using the remote terminal(operation 304). The maintenance data may include a record of everyaction performed by a maintainer while using the remote terminal as themaintainer traversed through different pages presented at the remoteterminal while troubleshooting avionics faults. The automaticperformance of operations 302 and 304 may reduce human errors and reducedocumenting workloads when maintenance actions are documented.

The example process 300 includes automatically recording in amaintenance database the fault data, testing data, maintenance data, andstatus data retrieved from the CMC and the maintenance data collectedfrom the remote terminal during maintenance operations (operation 306).After completing maintenance operations, a report identifying datarecorded in the maintenance database during the performance ofmaintenance operations can be automatically generated (operation 308).

The example process 300 includes automatically populating information ina plurality of fields in a maintenance work log (operation 310). Theplurality of fields in the maintenance work log may include a partnumber field, a serial number field related to the part number field, adescription field related to the part number field wherein theinformation populated in the description field includes a description ofactions performed by aircraft maintainer personnel on avionics systemsof the aircraft, and a time in service field related to the part numberfield.

The example process 300 includes automatically updating fields in alisting of life limited parts (operation 312). The life limited partsfields may include a name of a part, a part number associated with thepart, a serial number associated with the part, a date of installationof the part, a total time in-service for the part, a date the part wasremoved, and a signature and certification number for a personperforming troubleshooting regarding the part.

The example process 300 includes automatically alerting the maintainerpersonnel to complete certain pre-determined fields not automaticallypopulated by the processor but mandated for completion by governingauthority (operation 314). The alerting may include using an audiblealert, a visual alert on a display screen, or a combination of both anaudible and a visual alert.

FIG. 4 is a process flow chart depicting an example process 400 in anaircraft maintenance system for automatically recommending maintenancesteps to maintenance personnel. The order of operation within theprocess is not limited to the sequential execution as illustrated inFIG. 4, but may be performed in one or more varying orders as applicableand in accordance with the present disclosure.

The example process 400 includes retrieving, via a processor on theaircraft, fault data, testing data, maintenance data, and status dataregarding LRUs on the aircraft via a CMC on the aircraft (operation402). The fault data may include fault information retrieved by the CMCregarding the LRU over the ASCB. The testing data may include theidentity of any diagnostic tests performed regarding the LRU and theresults from the performed diagnostic tests. The identity of diagnostictests performed may include the identity of ASCB parametersinvestigated. The testing data may also include the identity ofperformed electrical checks and the results therefrom. The electricalchecks may include tests for shorts performed by monitoring Smart andnon-Smart LRU configurations. The maintenance data may include dataidentifying aircraft avionics system configuration changes made duringthe maintenance operations (e.g., whether an LRU was replaced during themaintenance operations), data identifying whether an LRU was resetduring maintenance operations, and the identity of maintenance manualsreferred to for troubleshooting. The status data may include dataindicating the operational status of the LRU and configurationinformation regarding the LRU wherein the configuration information mayinclude the software and hardware configuration of the LRU and itsassociated non-smart LRUs.

The example process 400 also includes automatically collecting, from aremote terminal on the aircraft, maintenance data regarding maintenanceoperations performed by maintenance personnel using the remote terminal(operation 404). The maintenance data may include a record of everyaction performed by a maintainer while using the remote terminal as themaintainer traversed through different pages presented at the remoteterminal while troubleshooting avionics faults.

The example process 400 further includes automatically recording in amaintenance database the fault data, testing data, maintenance data, andstatus data retrieved from the CMC and the maintenance data collectedfrom the remote terminal during maintenance operations (operation 406).

The example process 400 includes retrieving stored data from themaintenance database (operation 408) and analyzing the retrieved data togenerate proposed maintenance actions (operation 410). Various machinelearning techniques and/or algorithms may be used to analyze the datafrom the maintenance database to form maintenance action suggestions formaintenance personnel. Finally, the example process 400 includesrecommending the proposed maintenance actions to maintainer personnelbased on the analysis of the data from the maintenance database(operation 412).

Described herein are techniques that may allow for the recording ofevery maintenance action performed by a maintainer on avionics systemsin an aircraft through comprehensive recording of maintenance actionsperformed by the maintainer while using a remote terminal fortroubleshooting avionics faults and by capturing performed maintenanceactions by reviewing aircraft data on aircraft buses. Also describedherein are techniques in an aircraft maintenance system forautomatically creating aircraft maintenance records and work logs duringaircraft maintenance operations. Additionally, described herein aretechniques in an aircraft maintenance system for recommending proposedmaintenance steps for troubleshooting faults to maintenance personnel.

In one embodiment, a processor-implemented method for automaticallycreating aircraft maintenance records and work logs during aircraftmaintenance operations is disclosed. The method comprises retrieving,using a processor, fault data, testing data, maintenance data, andstatus data regarding line replaceable units (LRUs) on an aircraft via acentral maintenance computer (CMC) on the aircraft; automaticallycollecting from a remote terminal on the aircraft data regardingmaintenance operations performed using the remote terminal;automatically recording, by the processor in a maintenance database, thefault data, testing data, maintenance data, status data, and dataregarding maintenance operations performed using the remote terminal;and automatically populating, by the processor using data in themaintenance database, information in a plurality of fields in amaintenance work log.

These aspects and other embodiments may include one or more of thefollowing features. The method may further comprise automaticallygenerating, by the processor, a report identifying data recorded in themaintenance database during the performance of maintenance operations.The method may further comprise automatically updating, by the processorusing data in the maintenance database, fields in a listing of lifelimited parts. The method may further comprise automatically alerting amaintainer to complete certain pre-determined fields not automaticallypopulated by the processor but mandated for completion by governingauthority. The method may further comprise analyzing data from themaintenance database to generate proposed maintenance actions andrecommending the proposed maintenance actions to maintainer personnel.The fault data may comprise fault information retrieved by the CMCregarding at least one of the LRUs. The testing data may comprise theidentity of any diagnostic tests performed regarding at least one of theLRUs and results from the performed diagnostic tests. The identity ofperformed diagnostic tests may comprise the identity of ASCB (avionicssystem communication bus) parameters investigated. The testing data maycomprise data identifying performed electrical checks and the resultstherefrom, wherein the electrical checks comprise tests for shortsperformed by monitoring smart and non-smart LRU configurations. Themaintenance data may comprise data identifying aircraft avionics systemconfiguration changes made during the maintenance operations; dataidentifying whether an LRU was reset during maintenance operations; anddata identifying maintenance manuals referenced for troubleshooting. Thestatus data may comprise data indicating the operational status of atleast one of the LRUs and configuration information regarding at leastone of the LRUs wherein the configuration information includes thesoftware and hardware configuration of the LRU and its associatednon-smart LRUs. The data regarding maintenance operations performedusing the remote terminal may comprise a record of every actionperformed by a maintainer using the remote terminal as the maintainertraversed through different pages presented at the remote terminal whiletroubleshooting avionics faults. The plurality fields in a maintenancework log may comprise a part number field, a serial number field relatedto the part number field, a description field related to the part numberfield wherein the information populated in the description fieldincludes a description of actions performed by aircraft maintainerpersonnel on avionics systems of the aircraft, and a time in servicefield related to the part number field. The life limited parts fieldsmay comprise a name of a part, a part number associated with the part, aserial number associated with the part, a date of installation of thepart, a total time in-service for the part, a date the part was removed,and a signature and certification number for a person performingtroubleshooting regarding the part.

In another embodiment, a maintenance record creation module configuredto automatically create aircraft maintenance records and work logsduring aircraft maintenance operations is disclosed. The maintenancerecord creation module comprises one or more processors on an aircraftconfigured by programming instructions on non-transient computerreadable media. The maintenance record creation module is configured toretrieve fault data, testing data, maintenance data, and status dataregarding line replaceable units (LRUs) on an aircraft via a centralmaintenance computer (CMC) on the aircraft; automatically collect, froma remote terminal on the aircraft, data regarding maintenance operationsperformed using the remote terminal; automatically record, in amaintenance database, the fault data, testing data, maintenance data,status data, and data regarding maintenance operations performed usingthe remote terminal; and automatically populate, using data in themaintenance database, information in a plurality of fields in amaintenance work log.

These aspects and other embodiments may include one or more of thefollowing features. The maintenance record creation module may befurther configured to automatically generate a report identifying datarecorded in the maintenance database during the performance ofmaintenance operations. The maintenance record creation module may befurther configured to automatically update, using the data in themaintenance database, fields in a listing of life limited parts. Themaintenance record creation module may be further configured toautomatically alert a maintainer to complete certain pre-determinedfields not automatically populated by the processor but mandated forcompletion by governing authority.

In another embodiment, an aircraft equipped with a maintenance systemconfigured to automatically create aircraft maintenance records and worklogs during aircraft maintenance operations is disclosed. The aircraftcomprises a plurality of line replaceable units (LRUs), a centralmaintenance computer (CMC) configured to communicate with the LRUs viaan avionics system communication bus, and a remote terminal on theaircraft. The remote terminal is configured to: retrieve fault data,testing data, maintenance data, and status data regarding the LRUs viathe CMC; automatically collect data regarding maintenance operationsperformed using the remote terminal; automatically record in amaintenance database the fault data, testing data, maintenance data,status data, and data regarding maintenance operations performed usingthe remote terminal; automatically populate, using data in themaintenance database, information in a plurality of fields in amaintenance work log; automatically generate a report identifying datarecorded in the maintenance database during the performance ofmaintenance operations; automatically update, using data in themaintenance database, fields in a listing of life limited parts; andautomatically alert a maintainer to complete certain pre-determinedfields not automatically populated by the processor but mandated forcompletion by governing authority.

These aspects and other embodiments may include one or more of thefollowing features. The remote terminal may be further configured toanalyze data from the maintenance database to generate proposedmaintenance actions and recommend the proposed maintenance actions tomaintainer personnel.

Those of skill in the art will appreciate that the various illustrativelogical blocks, modules, circuits, and algorithm steps described inconnection with the embodiments disclosed herein may be implemented aselectronic hardware, computer software, or combinations of both. Some ofthe embodiments and implementations are described above in terms offunctional and/or logical block components (or modules) and variousprocessing steps. However, it should be appreciated that such blockcomponents (or modules) may be realized by any number of hardware,software, and/or firmware components configured to perform the specifiedfunctions. To clearly illustrate this interchangeability of hardware andsoftware, various illustrative components, blocks, modules, circuits,and steps have been described above generally in terms of theirfunctionality. Whether such functionality is implemented as hardware orsoftware depends upon the particular application and design constraintsimposed on the overall system. Skilled artisans may implement thedescribed functionality in varying ways for each particular application,but such implementation decisions should not be interpreted as causing adeparture from the scope of the present invention. For example, anembodiment of a system or a component may employ various integratedcircuit components, e.g., memory elements, digital signal processingelements, logic elements, look-up tables, or the like, which may carryout a variety of functions under the control of one or moremicroprocessors or other control devices. In addition, those skilled inthe art will appreciate that embodiments described herein are merelyexemplary implementations.

The various illustrative logical blocks, modules, and circuits describedin connection with the embodiments disclosed herein may be implementedor performed with a general-purpose processor, a digital signalprocessor (DSP), an application specific integrated circuit (ASIC), afield programmable gate array (FPGA) or other programmable logic device,discrete gate or transistor logic, discrete hardware components, or anycombination thereof designed to perform the functions described herein.A general-purpose processor may be a microprocessor, but in thealternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration.

The steps of a method or algorithm described in connection with theembodiments disclosed herein may be embodied directly in hardware, in asoftware module executed by a processor, or in a combination of the two.A software module may reside in RAM memory, flash memory, ROM memory,EPROM memory, EEPROM memory, registers, hard disk, a removable disk, aCD-ROM, or any other form of storage medium known in the art. Anexemplary storage medium is coupled to the processor such that theprocessor can read information from, and write information to, thestorage medium. In the alternative, the storage medium may be integralto the processor. The processor and the storage medium may reside in anASIC. The ASIC may reside in a user terminal. In the alternative, theprocessor and the storage medium may reside as discrete components in auser terminal.

In this document, relational terms such as first and second, and thelike may be used solely to distinguish one entity or action from anotherentity or action without necessarily requiring or implying any actualsuch relationship or order between such entities or actions. Numericalordinals such as “first,” “second,” “third,” etc. simply denotedifferent singles of a plurality and do not imply any order or sequenceunless specifically defined by the claim language. The sequence of thetext in any of the claims does not imply that process steps must beperformed in a temporal or logical order according to such sequenceunless it is specifically defined by the language of the claim. Theprocess steps may be interchanged in any order without departing fromthe scope of the invention if such an interchange does not contradictthe claim language and is not logically nonsensical.

Furthermore, depending on the context, words such as “connect” or“coupled to” used in describing a relationship between differentelements do not imply that a direct physical connection must be madebetween these elements. For example, two elements may be connected toeach other physically, electronically, logically, or in any othermanner, through one or more additional elements.

While at least one exemplary embodiment has been presented in theforegoing detailed description of the invention, it should beappreciated that a vast number of variations exist. As an example, inother embodiments the example processes 200, 300, 400, and 500 may beperformed by an engine-mounted communication module. It should also beappreciated that the exemplary embodiment or exemplary embodiments areonly examples, and are not intended to limit the scope, applicability,or configuration of the invention in any way. Rather, the foregoingdetailed description will provide those skilled in the art with aconvenient road map for implementing an exemplary embodiment of theinvention. It being understood that various changes may be made in thefunction and arrangement of elements described in an exemplaryembodiment without departing from the scope of the invention as setforth in the appended claims.

What is claimed is:
 1. A processor-implemented method for automaticallycreating aircraft maintenance records and work logs during aircraftmaintenance operations, the method comprising: retrieving, using aprocessor, fault data, testing data, maintenance data, and status dataregarding line replaceable units (LRUs) on an aircraft via a centralmaintenance computer (CMC) on the aircraft; automatically collectingfrom a remote terminal on the aircraft data regarding maintenanceoperations performed using the remote terminal; automatically recording,by the processor in a maintenance database, the fault data, testingdata, maintenance data, status data, and data regarding maintenanceoperations performed using the remote terminal; and automaticallypopulating, by the processor using data in the maintenance database,information in a plurality of fields in a maintenance work log.
 2. Themethod of claim 1, further comprising: automatically generating, by theprocessor, a report identifying data recorded in the maintenancedatabase during the performance of maintenance operations.
 3. The methodof claim 1, further comprising: automatically updating, by the processorusing data in the maintenance database, fields in a listing of lifelimited parts.
 4. The method of claim 1, further comprising:automatically alerting a maintainer to complete certain pre-determinedfields not automatically populated by the processor but mandated forcompletion by governing authority.
 5. The method of claim 1, furthercomprising: analyzing data from the maintenance database to generateproposed maintenance actions; and recommending the proposed maintenanceactions to maintainer personnel.
 6. The method of claim 1, wherein thefault data comprises: fault information retrieved by the CMC regardingat least one of the LRUs.
 7. The method of claim 1, wherein the testingdata comprises: the identity of any diagnostic tests performed regardingat least one of the LRUs; and results from the performed diagnostictests.
 8. The method of claim 7, wherein the identity of performeddiagnostic tests comprise: the identity of ASCB (avionics systemcommunication bus) parameters investigated.
 9. The method of claim 7,wherein the testing data further comprises data identifying performedelectrical checks and the results therefrom, wherein the electricalchecks comprise tests for shorts performed by monitoring smart andnon-smart LRU configurations.
 10. The method of claim 1, wherein themaintenance data comprises: data identifying aircraft avionics systemconfiguration changes made during the maintenance operations; dataidentifying whether an LRU was reset during maintenance operations; anddata identifying maintenance manuals referenced for troubleshooting. 11.The method of claim 1, wherein the status data comprises: dataindicating the operational status of at least one of the LRUs andconfiguration information regarding at least one of the LRUs wherein theconfiguration information includes the software and hardwareconfiguration of the LRU and its associated non-smart LRUs.
 12. Themethod of claim 1, wherein the data regarding maintenance operationsperformed using the remote terminal comprises a record of every actionperformed by a maintainer using the remote terminal as the maintainertraversed through different pages presented at the remote terminal whiletroubleshooting avionics faults.
 13. The method of claim 1, wherein theplurality fields in a maintenance work log comprises: a part numberfield, a serial number field related to the part number field, adescription field related to the part number field wherein theinformation populated in the description field includes a description ofactions performed by aircraft maintainer personnel on avionics systemsof the aircraft, and a time in service field related to the part numberfield.
 14. The method of claim 3, wherein the life limited parts fieldscomprises: a name of a part, a part number associated with the part, aserial number associated with the part, a date of installation of thepart, a total time in-service for the part, a date the part was removed,and a signature and certification number for a person performingtroubleshooting regarding the part.
 15. A maintenance record creationmodule configured to automatically create aircraft maintenance recordsand work logs during aircraft maintenance operations, the maintenancerecord creation module comprising one or more processors on an aircraftconfigured by programming instructions on non-transient computerreadable media, the maintenance record creation module configured to:retrieve fault data, testing data, maintenance data, and status dataregarding line replaceable units (LRUs) on an aircraft via a centralmaintenance computer (CMC) on the aircraft; automatically collect, froma remote terminal on the aircraft, data regarding maintenance operationsperformed using the remote terminal; automatically record, in amaintenance database, the fault data, testing data, maintenance data,status data, and data regarding maintenance operations performed usingthe remote terminal; and automatically populate, using data in themaintenance database, information in a plurality of fields in amaintenance work log.
 16. The maintenance record creation module ofclaim 15, further configured to: automatically generate a reportidentifying data recorded in the maintenance database during theperformance of maintenance operations.
 17. The maintenance recordcreation module of claim 15, further configured to: automaticallyupdate, using the data in the maintenance database, fields in a listingof life limited parts.
 18. The maintenance record creation module ofclaim 15, further configured to: automatically alert a maintainer tocomplete certain pre-determined fields not automatically populated bythe processor but mandated for completion by governing authority.
 19. Anaircraft equipped with a maintenance system configured to automaticallycreate aircraft maintenance records and work logs during aircraftmaintenance operations, the aircraft comprising: a plurality of linereplaceable units (LRUs); a central maintenance computer (CMC)configured to communicate with the LRUs via an avionics systemcommunication bus; and a remote terminal on the aircraft configured to:retrieve fault data, testing data, maintenance data, and status dataregarding the LRUs via the CMC; automatically collect data regardingmaintenance operations performed using the remote terminal;automatically record in a maintenance database the fault data, testingdata, maintenance data, status data, and data regarding maintenanceoperations performed using the remote terminal; automatically populate,using data in the maintenance database, information in a plurality offields in a maintenance work log; automatically generate a reportidentifying data recorded in the maintenance database during theperformance of maintenance operations; automatically update, using datain the maintenance database, fields in a listing of life limited parts;and automatically alert a maintainer to complete certain pre-determinedfields not automatically populated by the processor but mandated forcompletion by governing authority.
 20. The aircraft of claim 19, whereinthe remote terminal is further configured to: analyze data from themaintenance database to generate proposed maintenance actions; andrecommend the proposed maintenance actions to maintainer personnel.